Repository navigation
docs: record the dialog and the read-only install runs - #2
Merged
Merged
Conversation
What was run after the check for a missing WebView2 runtime went in: - The optimised build from CI, with the loader pointed at an empty folder, showed the app's own dialog and no terminal, and exited with code 1 when the dialog was closed. A click on the link brought Microsoft's page up in the browser. - The app and an engine in a folder the account could not write to, which is what Program Files is to an ordinary account. The engine beside the app was started, its data folder was under the app data directory, and nothing was added to the folder of the app. Two questions for the maintainer came out of the second: whether the provider cache of an installed app belongs in the roaming profile, and whether it should be the one the stackql command shell uses. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documentation only. It records two runs made after #1 was merged, and two questions that came out of them.
What was run
stackql.exewere put in a folder the account could read and run from but not write to, which is whatProgram Filesis to an ordinary account, and the app was started with that folder as its working folder. It started the engine beside it, the engine's data folder was under the app data directory, and nothing was added to the folder of the app.Not run: the real
Program Files, which needs an administrator, and a machine that truly has no WebView2 runtime.Questions for the maintainer
stackqlcommand shell the MSI installs, which is.stackqlin the home folder. Today each has its own, so a provider installed in one is not seen in the other.Generated with Claude Code